AFO 131 – Input from file

131.1 Introduction[//]

After choosing this AFO, the following form will be displayed:

Fields on the screen

Input from file: You can enter free text here, but must ensure path and file names are correct. Alternatively you can click on the icon next to the field. The form will reapper with a different first field:

You can use the Browse button to browse for files on your local workstation or network. Clicking on the pencil icon will revert to the original free text field.

Note:

This can be a file either on your local workstation or the Vubis server. However the browse button only browses the local PC, so if the file is on the server you will need to know the exact file path. The system looks for the file path on the server first. If the file is not found there, it puts up another window where you can browse for the file again (or enter the correct path and file name). This second window will only appear after you have tried to start the process.

Load profile: select the input/output profile that you want to use for loading records from the dropdown list. Be sure to create the input/output profile in AFO 133 that you need for loading, before using the Database loader window.

First record and Last record: Leave these to their default values (1 and 99999999) to process complete files. You can optionally set them differently to load only part of a file.

Check Import, Conversion and Load to load a title file whereby the data will be automatically converted to the appropriate fields and subsequently indexed.

Flip authority headings: check the box when you are loading authority records. Any see-reference in the authority database receiving the authority records, that match a loading authority record, will be converted (flipped) into the authority record. Otherwise, the loading authority record will not be loaded due to conflicts with the see-references.

Skip indexing check box: check this box if you want to load records without indexing the records as they are loaded. Use this option to save time when you are loading a large number of records (for example, when loading a new database). The loaded records can be indexed in a separate process, after all the records have been loaded.

Test database load check box: to turn on the test mode for the Database loader window. The system will do all the actions that you specify in the Database loader window, but will not save the records in the database.

Clean up workfiles: check the box to clear the workfile of any records remaining from previous loading (import or input) processes.

After completing the data, click OK. The system will switch to the standard screen for scheduling processes, where you can choose from Online, Batch or Memory. However, if the file to be loaded is on the workstation, you SHOULD NOT choose Batch or Memory, even though the system permits this.  If you do, the job will fail, but you will not know until you look at Started Jobs in AFO 642.

After the import process is completed, a report will be displayed:

From this you can deduce how many records have been processed, how many of these were new titles and how many of these have been merged with existing titles “ “).

131.2 Load automatically[//]

The loader will check the filename for an asterisk (*). If this has been entered instead of a filename, all files in the specified directory will be processed by the import module.

·                All files not starting with "$OK$" will be processed

·                All files that have been processed will get the prefix "$OK$"

When an asterisk has been entered the system will keep looking for files in the specified directory  until the time specified in the field Stop automatic loading at (HH:MM) is reached. Entering nothing means “until the end of the day”, entering a time will ensure the process stops at that time.

Note:

The load process itself will not be stopped at this time.


·                     Document control - Change History

 

Version

Date

Change description

Author

1.0

April 2008

creation

 

2.0

September 2009

textual improvements
part of 2.0 updates